Client device, information processing system and associated methodology of accessing networked services

ABSTRACT

A system provides access to services from different servers via a common API. The system includes service-offering servers, a client that uses services offered by the service-offering servers, and an interchange server that acts as an intermediary when the client uses a service. The client communicates with the interchange server using a common API when the client uses service from the service-offering servers. The interchange server uses a unique API, which is unique to the service-offering server that offers the service being used by the client, to execute a processing sequence that is unique to the service-offering server. Thus client is able to use services offered by the service-offering servers with the use of a common API and without any need to use a different unique API for each service-offering server.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S.application Ser. No. 13/934,680 filed Jul. 3, 2013, which is acontinuation application of U.S. application Ser. No. 12/995,619 filedDec. 1, 2010, which is a National Phase of PCT/US09/51840 filed Jul. 27,2009, and claims the benefit of U.S. Application Ser. No. 61/137,241entitled “Media Interchange”, filed Jul. 28, 2008, and U.S. ApplicationSer. No. 61/086,235 entitled “System of Uploading and Downloading Imagesby Using an Interchange Server,” filed Aug. 5, 2008, the entire contentsof each of which are incorporated herein by reference.

TECHNICAL FIELD

The present advancements relate to a client device, such as a camera, toaccess services offered by service-offering servers managed by serviceproviders. For example, upload processing may be provided in which aclient device transmits user data such as image data and the like to aserver so as to store the uploaded data in a server database.

BACKGROUND ART

Various types of services are accessible via a network. For example, aservice that allows user data such as images captured by a digitalcamera or the like to be uploaded to a server for storage in a databasethat is managed by the server is known. A user may browse the imagesthat are stored in the database of the server on demand. In addition,the uploaded images can be made publicly accessible via a network,depending on user preferences. Such an image upload processing isdescribed in, for example, Japanese Unexamined Patent ApplicationPublication No. 2006-252152, incorporated herein by reference.

The types and modes of services offered differ from one service providerto another. A user can choose any service depending on their preference.

Service providers offering such an image upload service provide anindividual solution for uploading an image(s) via Internet browser, thatis, a solution unique to each individual service provider. For example,a client device can perform upload processing by means of the Internetbrowser. However, generally speaking, this processing is difficultbecause there are many restrictions unique to the Internet browser.

In order to improve usability, some mobile devices such as some digitalcameras have, for example, an upload processing execution program thathas been stored in a memory thereof in advance to be used for uploadinga photographed image. Or, as another example, such a program isdownloaded from a server and then stored in the memory of a mobiledevice such as a camera. Upload processing is performed with the use ofthe stored upload-dedicated program.

However, many of such upload processing programs are unique torespective service providers. That is, in order to use an image uploadservice that is offered by a certain service provider, a dedicatedprogram that is unique to the above-mentioned certain service provideris necessary.

When a dedicated program that uniquely corresponds to a certain serviceprovider is used in a client device such as a digital camera, the clientuses an API (Application Programming Interface) that is unique to theservice provider. The API is the unit of a program for the execution ofpredetermined processing. As a certain API is called up, predeterminedprocessing that is specified in the called API is performed. Forexample, an API is set so as to correspond to each of server connectionprocessing, login processing, upload processing, and the like. A clientcan execute a series of processing with the use of these APIs.

In the majority of cases, such API is unique to each service provider.That is, a dedicated API that corresponds to login processing, uploadprocessing, or the like that is specified by each service provider isset. Accordingly, a client is required to use such a dedicated API.

As explained above, a service provider that offers an image uploadservice sets a plurality of APIs that are unique to services of its own.The service provider allows a client to use these APIs so as to performupload processing. Through API application processing explained above,upload processing such as the creation of upload data that is inconformity with an acceptable data format that is unique to the serviceprovider, client-server communication processing, and the like isexecuted. By this means, upload processing that is free from errors isensured.

If a client uses services offered by one service provider only, it isenough to install a program/API that uniquely corresponds to theabove-mentioned one service provider at the client side. However, in apractical sense, there are many service providers who offer image uploadservices. Therefore, in order to allow a user to freely select a serviceprovider among them, it is necessary to install many programs/APIs,which respectively correspond to all service providers, on the client.This is not desirable for a client device such as a camera that has alimited memory space.

In addition, programs/APIs are subject to change and/or update due to,for example, change in the modes of services offered by serviceproviders. If such change and/or update is effected after a clientdevice in which a plurality of APIs and programs that corresponds toimage upload services offered by a plurality of service providers isinstalled has been supplied to a user, it becomes necessary at theclient side to update the programs/APIs. If a user is required toperform such updating processing, it places a burden on the user.Moreover, there is a risk of the occurrence of a processing error.

SUMMARY

In view of the foregoing, the present advancements provide clientdevice, an information processing system, an information processingmethod, and a computer readable medium for accessing a plurality ofservice-offering servers via a common program and a common API.

The present disclosure provides a method of causing an interchangeserver to intermediate communication between a client device and aplurality of service-offering servers. A user interface is generated atthe client device in accordance with a common API that is independent ofthe plurality of service-offering servers. Input data entered into theuser interface is received at the interchange server. The input dataincludes selection of a service corresponding to at least one of theplurality of service-offering servers. The input data is translatedaccording to at least one service-specific API associated with the atleast one service-offering server corresponding to the selected service.The service-specific API is stored in an electronic memory of theinterchange server as part of a plurality of different service-specificAPIs that respectively correspond to the plurality of service-offeringservers. The translated data is transmitted from the interchange serverto the at least one service-offering server in accordance with the atleast one service-specific API, and a response from the at least oneservice-offering server is translated and transmitted to the client inaccordance with the common API.

Other objects, features, and advantages of the present disclosure willbe fully understood from the following detailed description of exemplaryembodiments of the invention read in conjunction with accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the advancements and many of theattendant advantages thereof will be readily obtained as the samebecomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings. However, the accompanying drawings and their exemplarydepictions do not in any way limit the scope of the advancementsembraced by this specification. The scope of the advancements embracedby the specification and drawings are defined by the words of theaccompanying claims.

FIG. 1 is a diagram of an information processing system according to anexemplary embodiment of the present disclosure;

FIG. 2 is a table of modes of services that are offered by serviceproviders;

FIG. 3 is an additional table of modes of services that are offered byservice providers;

FIG. 4 is a processing sequence diagram of a process executed between aclient, an interchange server, and a service-offering server accordingto an exemplary embodiment of the present disclosure;

FIG. 5 is another processing sequence diagram of processing executedbetween a client, an interchange server, and a service-offering serveraccording to an exemplary embodiment of the present disclosure;

FIG. 6 is a further processing sequence diagram of processing executedbetween a client, an interchange server, and a service-offering serveraccording to an exemplary embodiment of the present disclosure;

FIG. 7 is a diagram of service detail information that is provided bythe interchange server to the client according to an exemplaryembodiment of the present disclosure;

FIG. 8 is a diagram of a user interface (UI) for image uploadprocessing, which is displayed on the display screen of the client,according to an exemplary embodiment of the present disclosure;

FIG. 9 is another diagram of a user interface (UI) for image uploadprocessing, which is displayed on the display screen of the client,according to an exemplary embodiment of the present disclosure;

FIG. 10 is a diagram of an image list that is displayed on the displayscreen of the client at the time of the browsing of uploaded imagesaccording to an exemplary embodiment of the present disclosure;

FIG. 11 is another diagram an image list that is displayed on thedisplay screen of the client at the time of the browsing of uploadedimages according to an exemplary embodiment of the present disclosure;

FIG. 12 is a flowchart of a URL selection processing sequence forselecting a URL corresponding to upload image(s) that is provided by theinterchange server to the client according to an exemplary embodiment ofthe present disclosure;

FIG. 13 is a sequence chart of APIs that are applied to processingbetween the client, the interchange server, and the service-offeringserver according to an exemplary embodiment of the present disclosure;

FIG. 14 is another sequence chart of APIs that are applied to processingbetween the client, the interchange server, and the service-offeringserver according to an exemplary embodiment of the present disclosure;

FIG. 15 is a further sequence chart of APIs that are applied toprocessing between the client, the interchange server, and theservice-offering server according to an exemplary embodiment of thepresent disclosure; and

FIG. 16 is a diagram of the hardware configurations for each of theclient, the interchange server, and the service-offering serveraccording to an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION

In the following, the present advancement will be discussed bydescribing a preferred embodiment, and by referring to the accompanyingdrawings. However, those skilled in the art will realize otherapplications and modifications within the scope of the invention asdefined in the enclosed independent claims.

FIG. 1 is an example of the configuration of an information processingsystem according to an exemplary embodiment of the invention thatincludes a client 101, another client 102, a Web server 105, aninterchange server 110, and service-offering servers A-F, 121-126. Theseapparatuses are configured in such a manner that they can performcommunication via a network.

The service-offering servers 121-126 are servers that are operated byservice providers A-F who offer services to the clients 101 and 102.Specifically, for example, the service-offering servers 121-126 storeimage data, which is uploaded by a client, into a database and managesthe stored data. Images that are uploaded by clients are managed on aclient-by-client basis so that the images are available for browsing asdemanded by the client user. In addition, depending on user setting, itis possible to make the images available for public access via anetwork.

Each of the service-offering servers 121-126 is a server that isoperated by a service provider A-F that is different from others.Although these service providers A-F are the same as one another in thatthey offer an image upload service, modes of services offered therebydiffer from one individual service provider to another.

FIGS. 2 and 3 are examples of services offered by the service providersA-F. In FIGS. 2-3 an “O” represents a service mode offered by aservice-offering server, an “X” represents a service mode not offered bythe service-offering server and a “-” represents a table entry that isnot applicable to the service-offering server.

Although the services offered by the service providers A-F have acommonality in that each of them manages images that are uploaded byclients, specific modes of services offered thereby differ from oneservice provider to another, an example of which is shown in FIGS. 2 and3.

The following describes the service modes included in FIGS. 2-3.

(1) The “Compatible Picture Format” indicates which one, or both, of theuploading of a still picture and the uploading of a moving picture isallowed under each service.

(2) The “Public/Non-public Setting” indicates whether it is possible toset an image that is uploaded by a client (user) as a publicly availableimage/non-public image or not under each service.

(3) The “Album Function” indicates whether it is possible to set analbum as a unit of the management of images that are uploaded by aclient or not under each service.

(4) The “Album Title Entry” indicates whether the inputting of a titlefor an album that is set for a group of images that are uploaded by aclient is accepted or not under each service.

(5) The “Image Title Entry” indicates whether the titling of an imagethat is uploaded by a client is allowed or not under each service.

(6) The “Image Description Entry” indicates whether the inputting of anexplanation text of an image that is uploaded by a client is allowed ornot under each service.

(7) The “Tag Entry” indicates whether the affixing of a tag to an imagethat is uploaded by a client is allowed or not under each service.

(8) The “Log-in Parameter” indicates the type of a login parameter thatis required by each service A-F at the time of the execution ofuploading from a client.

(9) The “Still Picture Maximum Size” indicates the maximum size of astill image that can be uploaded, that is, the uploading thereof isallowed, under each service.

(10) The “Moving Picture Maximum Size” indicates the maximum size of amoving image that can be uploaded, that is, the uploading thereof isallowed, under each service.

(11) The “Moving Picture Maximum Time” indicates the maximum length oftime for a moving image that can be uploaded, that is, the uploadingthereof is allowed, under each service.

(12) The “Maximum Content Number” indicates the maximum number ofcontent that can be uploaded, that is, the uploading thereof is allowed,under each service.

(13) The “Service Logo” indicates the service logo of each service.

(14) The “Service Trademark Credit Line” indicates the text of thetrademark credit of each service.

(15) The “Upload Order” indicates the sequential order of thearrangement of images that are uploaded by a client and then arranged atthe time of and/or for browsing under each service.

(16) The “Server-side Automatic Processing” indicates processing which aserver automatically performs at the time of upload processing undereach service.

As will be understood from FIGS. 2 and 3, although the services offeredby the service providers A-F have a commonality in that each of themmanages images that are uploaded by clients, specific modes of servicesoffered thereby differ from one service provider to another. It shouldbe noted that FIGS. 2 and 3 are merely exemplary, and other modes ofservices are possible. As such, the present advancement is not limitedin any way by the modes of service included in FIGS. 2-3.

Each of the service providers A-F corresponding to service-offeringservers 121-126 of FIG. 1 offers, to clients, an image upload servicethat is unique as explained above. Therefore, it is typical that theservice provider A-F provides a program/API that is required for uploadprocessing to clients. Clients can perform upload processing while usingthe program/API that is provided by the service provider 121-126.

However, as has already been explained above, if it is assumed that aclient uses services that are offered by various service providers A-Fit is necessary for the client to memorize all programs/APIs that areoffered by these service providers A-F in its memory. In addition, forexample, when the updating of a program or the addition of a new APIoccurs, it is necessary to respond thereto at the client side.

An information processing system according to the present advancement isprovided with an interchange server 110 in order to reduce the burden ofa client.

Each of the clients 101 and 102 does not perform direct communicationwith the service-offering server 121-126 but performs indirectcommunication therewith. That is, the client 101 communicates with theinterchange server 110, whereas the client 102 communicates with the Webserver 105.

The client 101 is a client that stores programs/APIs for the executionof upload processing in, for example, a memory unit, and executesprocessing while using them. When using a service offered by theservice-offering server 121-126 of each service provider, the client 101uses a common program/API, which is common to all of these serviceproviders, so as to perform communication with the interchange server110. That is, the client 101 executes the uploading of an image, thebrowsing of an image, or the like while utilizing the service-offeringserver 121-126 through the intermediary of the interchange server 110.

The client 102 is a client that does not have any program/API that isapplied to upload processing. Although the client 102 does not directlycommunicate with the interchange server 110, the client 102 has abrowsing function and performs the uploading of an image by means of aWeb page, which is offered by the Web server 105. That is, the client102 executes the uploading of an image, the browsing of an image, or thelike while utilizing the service-offering server 121-126 through theintermediary of the Web server 105 and the interchange server 110.

The Web server 105 is located somewhere between the interchange server110 and the client 102. On the basis of data that is offered by theinterchange server 110, the Web server 105 creates a web page that ismade up of HTML data. Then, the Web server 105 provides the created webpage to the client 102. In addition, the Web server 105 transfers datathat is sent from the client 102 to the interchange server 110. Forexample, the Web server 105 transfers upload data to the interchangeserver 110.

The client 101 performs processing with the use of a common program/APIfor communication with the interchange server 110 when any of servicesoffered by the service-offering servers 121-126 is used. The same holdstrue for the Web server 105. Therefore, the Web server 105 has the sameprogram execution function as that of the client 101.

Next, with reference to FIGS. 4-6, an explanation is given of acommunication processing sequence that is executed, when a client uses aservice that is offered by any of the service-offering servers 121-126,between the client and the service-offering server through theintermediary of an interchange server.

Each of FIGS. 4-6 shows a client-side user, a client, an interchangeserver, and a service-offering server in the order of appearance hereinwith the user being the leftmost one. Note that the client in FIGS. 4-6corresponds to the client 101 of FIG. 1. The interchange server in FIGS.4-6 corresponds to the interchange server 110 in FIG. 1. Theservice-offering server in FIGS. 4-6 corresponds to any one of theservice-offering servers 121-126 in FIG. 1.

Each process sequence of FIGS. 4-6 is explained below.

First of all, in a step S11, a client user launches a client programthat has been stored in a client in advance. The client program is acommon program that is run for a service of any of the service-offeringservers 121-126.

In a step S12, the client makes a request for “a list of currentlyavailable services” to the interchange server in accordance with thelaunched program. When the client submits such a request, the client maytransmit client local area information and client language informationas parameters in addition to the request. Note that the parametertransmission thereof can be performed as processing that is inaccordance with user setting.

In a step S13, the interchange server returns the requested list ofcurrently available services to the client. The interchange server hasreceived information on latest services from the service-offeringservers 121-126 shown in FIG. 1 in advance. The interchange servercreates a service list that is in accordance with the pre-receivedinformation, and then provides the service list to the client. If theinterchange server has received local area information and the languageinformation from the client, the interchange server may perform thefiltering of the service list on the basis of the received information.For example, if the local area of the client is Japan and the languageof the client is Japanese, the interchange server provides aJapanese-version list to the client.

Moreover, the interchange server may create and/or update the servicelist periodically without input from the client device. For example, theinterchange server may update the service list in response tonotification of updated services by the service-offering servers, inresponse to discovery of new service-offering servers, and/or inresponse to the unavailability of service-offering servers whoseservices are included in the service list. As can be appreciated by oneskilled in the art, the cases of service list update by the interchangeserver are merely exemplary, and other cases are possible withoutdeparting from the scope of the present disclosure.

In a step S14, the client displays the list of currently availableservices that has been received from the interchange server on a displayscreen as, for example, user interface (UI) information. The servicelist is a list that shows services offered by each service provider. Theservice list is a UI that is set in such a manner that a user can selectany service. For example, the service list contains:

Service Provider A: Still Picture Upload Service, Browse Service

Service Provider B: Still Picture Upload Service, Browse Service

Service Provider C: Still Picture Upload Service, Browse Service

Service Provider D: Moving Picture Upload Service, Browse Service

Service Provider E: Moving Picture Upload Service, Browse Service

In a step S15, the client user selects a specific service from theservice list, and then commands the execution of processing, forexample, the uploading of an image.

In a step S16, the client makes a request for detailed information onthe selected service (i.e., specified service) to the interchange serveron the basis of the inputted user instructions.

In a step S17, the interchange server transmits the detailed informationon the selected service to the client. As has already been explainedabove, the interchange server has received detailed information onlatest services from the service-offering servers 121-126 shown in FIG.1 in advance. The interchange server selects information thatcorresponds to the service selected by the user out of the pre-receivedlatest service detail information, and then provides the selectedinformation to the client.

Before transmitting the detailed information, the interchange server mayvalidate the client request for detailed information. For example, theinterchange server may store machine-specific information pertaining tothe client, and may use the machine-specific information to validate theclient request. Such machine-specific information include, withoutlimitation, a device ID specific to the client and a client version ID.However, as can be appreciated by one skilled in the art, othermachine-specific information is also possible, such as a serial numberor MAC ID.

The machine-specific information is not transmitted from the client tothe interchange server. Instead, it is stored in the interchange serverbeforehand. The client may then use the machine-specific information togenerate a checksum that is appended to the request. The interchangeserver may then validate the request based on the appended checksum byusing the machine-specific information. Once, the request is validated,the interchange server transmits the detailed information to the client.

FIG. 7 is an example of the service detail information that is providedby the interchange server to the client. In FIG. 7, the service detailinformation has, for example, an extensible markup language (XML) dataformat, but may also be provided in a Javascript object notation (JSON)format. Other formats for the detailed information, are also possiblewithout departing from the scope of the present disclosure. As such theformat of the detailed information in no way limits the scope of thepresent advancements.

The service detail information contains information that is used for thegeneration of a user interface (UI) that is displayed on the displayscreen of the client when image upload processing is executed. Inaddition, the service detail information contains information on themode of an image that can be uploaded, for example, information as towhich one of the uploading of a still picture and the uploading of amoving picture is allowed. The service detail information furthercontains information on the size of an image, for example, informationon the size of a still picture or information on the size of a movingpicture. The service detail information further contains information onparameters that are required at the time of and/or for login. If thereis a plurality of images that should be uploaded, the service detailinformation further contains setting information on the sequential orderof images that are to be uploaded. It should be noted that the servicedetail information illustrated in FIG. 7 is merely a simplified example.That is, FIG. 7 does not show all of the service detail information. Oneof ordinary skill in the are will readily appreciate that other servicedetail information is possible without departing from the scope of thepresent advancement.

The service detail information contains information on the modes ofservices that have already been explained above while referring to FIGS.2 and 3. That is, the service detail information contains information on(1) Compatible Picture Format, (2) Public/Non-public Setting, (3) AlbumFunction, (4) Album Title Entry, (5) Image Title Entry, (6) ImageDescription Entry, (7) Tag Entry, (8) Log-in Parameter, (9) StillPicture Maximum Size, (10) Moving Picture Maximum Size, (11) MovingPicture Maximum Time, (12) Maximum Content Number, (13) Service Logo,(14) Service Trademark Credit Line, (15) Upload Order, and (16)Server-side Automatic Processing.

In a step S18, a client displays a user interface (UI) that is used forperforming image upload processing in accordance with the service detailinformation, which has been received from the interchange server, thatis, the selected information that corresponds to the service selected bythe user.

The user interface (UI) that is used for performing image uploadprocessing differs from one service to another, that is, depending onthe service selected by the user. That is, the user interface (UI) isgenerated in accordance with the service detail information thatcorresponds to the service provider, which was selected by theinterchange server in accordance with the user-selected information andthen sent to the client.

FIGS. 8 and 9 are examples of a user interface (UI) that is presented atthe client. FIG. 8 is a user interface (UI) that is used for performingimage upload processing and is generated in accordance with the servicedetail information corresponding to the service provider A. FIG. 9 is auser interface (UI) that is used for performing image upload processingand is generated in accordance with the service detail informationcorresponding to the service provider B.

In FIGS. 8 and 9, a user interface (UI) that is used for performingimage upload processing contains, for example, the following displaydata:

(a) An icon/logo 201 of the service provider.

(b) A log-in information input box 202 that is used for inputtinginformation that is necessary for login.

(c) An upload image setting box 203 that is used for setting an uploadimage(s).

(d) An upload image public/non-public checkbox 204 (shown for theservice A of FIG. 8 only).

(e) Album information setting fields 205 that are provided for a servicethat offers an album function (shown for the service B of FIG. 9 only).

In addition thereto, various kinds of information are displayed as theUI depending on the service. As will be readily appreciated by one ofordinary skill in the art, other user interfaces are also possiblewithout departing from the scope of the present advancement.

In addition, filtering processing may be performed so that, for example,any images that do not conform to the compatible picture format of theservice are not displayed. Moreover, the display of a trademark creditline, notandums, that is, dos and don'ts for uploading, right/licenseinformation (EULA), and the like is performed. The display of these isperformed on the basis of data that is contained in the service detailinformation that is provided by the interchange server to the client,which has already been explained above while referring to FIG. 7.

Referring back to the sequence charts of FIGS. 4-6, the communicationsequence is further explained below. In the step S18 of FIG. 4, the userinterface (UI) that is used for performing image upload processing, forexample FIGS. 8 and 9, is presented on the display of the client.

Next, in a step S19 of FIG. 5, the user inputs login information(authentication information) in the login information input box of thepresented user interface UI. The login information (authenticationinformation) differs from one service provider to another. The userinputs the login information in accordance with input instructions shownon the UI. For example, if the user uses the service A that is offeredby the service provider A shown in FIG. 8, the user inputs their username as the login information (authentication information) as promptedin a log-in information input box 202 a.

On the other hand, if the user uses the service B that is offered by theservice provider B the user interface of FIG. 9 is used. Therein, theuser inputs their e-mail address as the login information(authentication information) as prompted in a log-in information inputbox 202 b.

In a step S20, the client transmits the login information(authentication information) to the interchange server.

In a step S21, the interchange server transmits the login information(authentication information) to one of the service-offering servers ofthe service providers A-F that has already been selected by the user. Itshould be noted that a program/API that is provided for the transmissionof login information (authentication information) by the serviceprovider that has already been selected by the user is used for thislogin information transmission processing.

Upon the reception of the login information (authentication information)from the interchange server, the service-offering server verifies thereceived login information (authentication information). Then, if it isverified that the user is a client user/person who has due uploadauthority, the service-offering server accepts a login request. In astep S22, the service-offering server returns a login verificationresult (Success) to the interchange server and establishes acommunication connection for maintaining a session.

Next, in a step S23, the interchange server transfers the loginverification result (Success) to the client and issues a session ID formaintaining a communication session between the client and theinterchange server. Subsequent communication between the client and theinterchange server is performed with the additional notation of thesession ID as a parameter.

In a step S24, the user inputs information that is required for uploadprocessing; for example, the user sets an upload image(s) and the like.In this step, the user inputs necessary information with the use of theuser interface that is provided for image upload processing, a fewexamples of which have been explained earlier with reference to FIGS. 8and 9. The user creates an album and inputs a title and/or a commentwhere necessary. Then, the user issues upload instructions.

In a step S25, in response to the upload instructions issued by theuser, the client sends, that is, uploads, image data that includes animage(s) to be uploaded and meta data (e.g., comment) to the interchangeserver. If a plurality of images is uploaded, the sequential order ofthe uploading thereof is controlled in accordance with the serviceoffered by the service provider that is selected by the user. Suchcontrol information is also contained in the service detail informationthat has already been explained above while referring to FIG. 7.

The reason why the sequential order of the uploading of a plurality ofimages is changed depending on the service that is selected by the user,that is, depending on the service provider selected thereby, is that thesequential order of the display of a plurality of uploaded imagesdiffers from one service provider to another. In other words, it isbecause the sequence format of an image list that is provided for thebrowsing of uploaded images varies from one service provider to another.

For example, some service providers offer a list for browsing imagesthat are arranged in the order of the uploading thereof performed by aclient. That is, they offer a browsing list that shows the earliest(i.e., first) uploaded image as the first one and later uploaded imagesas subsequent ones that are arranged in accordance with the sequentialorder of the uploading thereof.

Other service providers offer a list for browsing images that arearranged in a sequential order reverse to the order of the uploadingthereof performed by a client. That is, they offer a browsing list thatshows the latest (i.e., last) uploaded image as the first one andearlier uploaded images as subsequent ones that are arranged inaccordance with an order reverse to the sequential order of theuploading thereof.

An example of such an image browse list is explained while referring toFIGS. 10 and 11. FIGS. 10 and 11 are lists for browsing uploaded imagesthat are offered by two service providers different from each other.

FIG. 10 is a list for browsing images that are arranged in thesequential order of the uploading thereof performed by a client. Thatis, FIG. 10 is an image browse list that shows the first image uploadedby a client as the first one and later images uploaded by the client assubsequent ones that are arranged in accordance with the sequentialorder of the uploading thereof.

FIG. 11 is a list for browsing images that are arranged in an orderreverse to the sequential order of the uploading thereof performed by aclient. That is, FIG. 11 is an image browse list that shows the lastimage uploaded by a client as the first one and earlier images uploadedby the client as subsequent ones that are arranged in accordance with anorder reverse to the sequential order of the uploading thereof.

If the arrangement of images contained in one image browse list that isoffered to a client by one service provider differs from the arrangementof images contained in another image browse list that is offered to theclient by another service provider, the client user who uses variouskinds of services might be confused. In order to prevent users frombeing confused, the sequential order of uploading images is changed insuch a manner that the arrangement of images contained in an imagebrowse list is always the same, regardless of which service provider isselected.

That is, when a client uploads a plurality of images in a sequentialmanner, the sequential order thereof is controlled so as to ensure thatthe order of display offered at the time of image browsing is always thesame, regardless of which service is selected.

For example, the display order of images in FIG. 10, that is, the orderof a list for browsing images that are arranged in the sequential orderof the uploading thereof by a client, is set as “normal order”. Thedisplay order of images in FIG. 11, that is, the order of a list forbrowsing images that are arranged in an order reverse to the sequentialorder of the uploading thereof by the client, is set as “reverse order”.

Under such a setting, if the service selected by the user is one that isoffered by a service provider who offers a “reverse-order” browsinglist, upload processing is performed after reversing the sequentialorder of a plurality of upload images when the client uploads theseimages.

On the other hand, if the service selected by the user is one that isoffered by a service provider who offers a “normal-order” browsing list,upload processing is performed without reversing the sequential order ofa plurality of upload images when the client uploads these images.

Since the sequential order of the uploading of images is controlled asexplained above, it is possible to browse images that are presented inthe form of a “normal-order” browsing list regardless of which serviceprovider is selected.

In the foregoing upload processing example, although an explanation isgiven under the assumption that each of all services presents a“normal-order” image list, it is not necessarily limited thereto. Thatis, upload processing may be performed under the setting in which a“reverse-order” image list is presented in each of all services. Undersuch a modified setting, if the service selected by the user is one thatis offered by a service provider who offers a “reverse-order” browsinglist, upload processing is performed without reversing the sequentialorder of a plurality of upload images when the client uploads theseimages.

On the other hand, if the service selected by the user is one that isoffered by a service provider who offers a “normal-order” browsing list,upload processing is performed after reversing the sequential order of aplurality of upload images when the client uploads these images.

Since the sequential order of the uploading of images is controlled asexplained above, it is possible to browse images that are presented inthe form of a “reverse-order” browsing list regardless of which serviceprovider is selected.

As explained above, when a plurality of images is uploaded in theimage-uploading step S25 of FIG. 5, control is executed so as to changethe sequential order of the transmission of the images depending on theservice selected by the user.

Next, in a step S26, the interchange server temporarily stores the imagedata that has been received from the client into a memory. Then, theinterchange server uploads the image data to the service-offering serverthat is selected by the user.

It should be noted that a program/API that is provided for uploadprocessing by the service provider that has already been selected by theuser is used for this upload processing.

In this upload processing, the interchange server adds informationand/or corrects information where necessary. For example, theinterchange server processes transmission information by affixing metadata (title, comment, and/or tag) to an image.

Specifically, for example, if data that has been transmitted from theclient to the interchange server does not satisfy upload formatconditions that are required by the service provider, the interchangeserver performs the processing of the data for uploading so as to meetthe required conditions.

For example, in some cases, the number of characters contained in acomment that is attached to an image that is included in upload datatransmitted from a client to the interchange server may not be inagreement with the acceptable number of characters for the selectedservice provider. As another example, required meta data that is notallowed to be omitted may not be affixed to an image. In such a case,the interchange server performs the addition of information and/orcorrection thereof to arrange the format thereof so as to ensure thatthat no uploading error occurs.

Next, in a step S27, the interchange server transmits upload data (e.g.,image(s), meta data, and the like) that contains an image(s) that hasbeen received from the client to the service-offering server selected bythe user.

The service-offering server receives the upload data from theinterchange server. Then, the service-offering server keeps and managesthe received upload data under the data management policy thereof.

Next, in a step S28 of FIG. 6, the service-offering server returns theresult of upload (e.g., Success/Failure) to the interchange server. Theservice-offering server may return, as the uploading result, a URL(s)that is set for the uploaded image(s) as information for accessing theuploaded image(s) to the interchange server.

In a step S29, the interchange server transmits the result of uploadtogether with URL information corresponding to the uploaded image(s),which have been received from the service-offering server, to theclient.

Upon the reception of the URLs corresponding to the uploaded images fromthe service provider, the interchange server may transfer the URLscorresponding to the uploaded images to the client without performingany processing thereon. Or, for example, in the flowchart of FIG. 12,the interchange server may select one URL out of the URLs correspondingto the uploaded images and then send the selected URL to the client.

The operation flow of FIG. 12 includes procedures for selecting one URLthat should be provided to the client where the selection is madedepending on the actual mode of upload taken by the client out of thefollowing three upload modes.

When a client has uploaded a single image, the interchange serverprovides a URL for direct link to the uploaded image to the client. Whena client has uploaded a plurality of images to a service-offering serverthat offers an album function, the interchange server provides the URLof the front page of an album to the client. When a client has uploadeda plurality of images to a service-offering server that does not offeran album function, the interchange server provides the URL of the frontpage of the user to the client.

The flowchart of FIG. 12 is explained below. First of all, in a stepS101, the interchange server makes a judgment as to whether the clienthas uploaded a plurality of images or not.

If it is judged in the step S101 that the client has uploaded a singleimage, the process moves on to a step S102. In the step S102, theinterchange server provides a URL for direct link to the single uploadedimage to the client.

If it is judged in the step S101 that the client has uploaded aplurality of images, the process moves on to a step S103. In the stepS103, the interchange server judges whether the upload destinationservice provider offers an album service or not. That is, theinterchange server confirms whether the upload destination serviceprovider offers a service for managing a group of a plurality of imagesuploaded in a batch transmission as an album or not.

If it is judged in the step S103 that the upload destination serviceprovider offers an album management service, the process goes to a stepS104. In the step S104, the interchange server provides the URL of analbum front page to the client.

On the other hand, if it is judged in the step S103 that the uploaddestination service provider does not offer an album management service,the process goes to a step S105. In the step S105, the interchangeserver provides the URL of a user front page to the client.

As explained above, the interchange server selects one URL and thenprovides the selected URL to the client. If such URL selectionprocessing is performed, it is possible for the user to browse images inan efficient manner while utilizing the optimally selected URL. Theinterchange server executes the URL selection processing explained aboveas procedures common to all service providers.

Referring back to FIG. 6, the entire sequence is further explainedbelow. In the step S29, the interchange server transmits the result ofupload together with URL information corresponding to the uploadedimage(s), which have been received from the service-offering server, tothe client.

Finally, in the step S30, the client displays the result of the uploadand the URL(s) on the display screen and then terminates the processing.The URL(s) is stored in the memory unit (nonvolatile memory) of theclient. The stored URL is used at the time of the execution of browsingprocessing.

In the foregoing description, it is assumed that the sequence explainedabove while referring to FIGS. 4-6 is performed as communicationprocessing between the client 101 and the service-offering server121-126 through the intermediary of the interchange server 110 of FIG.1.

If the sequence is performed as processing between the client 102 andthe service-offering server 121-126 through the intermediary of the Webserver 105 and the interchange server 110 of FIG. 1, the processingbetween the interchange server 110 and the service-offering server121-126 is performed as the same processing as that performed betweenthe interchange server and the service-offering server that is explainedabove with reference to FIGS. 4-6.

In addition, the processing between the interchange server 110 and theWeb server 105 is performed in the same manner as performed between theinterchange server and the client that is explained above with referenceto FIGS. 4-6. The processing between the client and the user that isexplained above with reference to FIGS. 4-6 is performed as theprocessing between the Web server 105, the client 102, and the user.

The Web server 105 creates a web page in an HTML data format inaccordance with the data that has been received from the interchangeserver 110. Then, the Web server 105 presents the created web page tothe client 102. The client 102 uses its browser function to display theweb page provided by the Web server 105.

The user uses the web page that is displayed on the client 102 as userinterface and performs the inputting of data, the setting of an uploadimage(s), and the like. Then, the user transmits data including theupload image(s) with the use of the web page to the Web server 105. Asdone by the client A, the Web server 105 uses a common program/API,which is common to all service providers, so as to perform communicationwith the interchange server 110. By this means, the Web server 105transmits upload information that has been received from the client 102to the interchange server 110.

Through such processing, the client 102, which is a client that does nothave any program/API that is applied to upload processing, can executethe same image upload processing as that of the client 101.

As explained above, when a service offered by any of theservice-offering servers 121-126 is used, it is not necessary for theclients 101 and 102 to switch to a program/API that is uniquely appliedto the selected service. This is thanks to the intermediary of theinterchange server.

When any service offered by the service-offering servers 121-126 isused, each of the client 101 and the Web server 105 can use a commonprogram/API for communications with the interchange server.

An example of the application of APIs is explained below while referringto FIGS. 13-15. Each of FIGS. 13-15 includes a client, an interchangeserver, and a service-offering server in the order of appearance hereinas viewed from left to right. The client of FIGS. 13-15 corresponds tothe client 101 of FIG. 1, or the Web server 102 that performscommunication with the client 102 of FIG. 1. The interchange servershown therein corresponds to the interchange server 110 of FIG. 1. Theservice-offering server shown therein corresponds to any of theservice-offering servers 121-126 of FIG. 1.

A set of sequence charts of FIGS. 13-15 include the sequence of theuploading of an image(s) by the client to the service-offering serverthrough the intermediary of the interchange server as has already beenexplained above while referring to FIGS. 4-6. The sequence charts ofFIGS. 13-15 are an example of an API that is used by the client (or Webserver) and an API that is used by the interchange server.

When any service that is offered by the service-offering servers 121-126of FIG. 1 is used, the client can use an API that is common thereto(i.e., common API). Upon the selection of one service at the clientside, the selected service is notified to the interchange server.Accordingly, it should be noted that, once one service has beendetermined at the client side, the interchange server uses an API thatcorresponds to the service selected by the client so as to performcommunication/processing with the service-offering server that offersthe selected service.

First of all, in a step S301, the client uses (i.e, applies) a commonAPI [GET services] so as to make a request for the acquisition of aservice list. The API [GET services] is an API that causes a programthat defines a sequence for making a request for a service list to theinterchange server to be executed. In a step S302, the interchangeserver transmits a service list to the client in response to the requestissued from the client.

Next, in a step S303, the client uses a common API [GET service] so asto make a request for the acquisition of service detail information. TheAPI [GET service] is an API that causes a program that defines asequence for making a request for service detail information to theinterchange server to be executed. Note that the client transmits theidentifier of the selected service to the interchange server when makinga request for service detail information to the interchange server.

In a step S304, in response to the request made by the client, theinterchange server sends service detail information that corresponds tothe service selected by the client. The service detail information is,for example, information that has been explained earlier while referringto FIG. 7.

Next, in a step S305 of FIG. 14, the client inputs login information inthe login information input box 202 of a user interface (UI) (refer toFIGS. 8 and 9) that is displayed on a display screen so as to be usedfor performing image upload processing on the basis of the servicedetail information. In this way, login processing is performed in thestep S305. The API used for login processing is a common API [GET login]in step S305 of FIG. 14. The API [GET login] is an API that causes aprogram that defines a sequence for transmitting login information tothe interchange server to be executed.

In response to the inputting of login information by the client, theinterchange server performs login to the service-offering server thatcorresponds to the service selected by the client. An API that isprovided by the service provider that corresponds to the serviceselected by the client is used for this login processing. That is, it isexecuted as login processing that corresponds to a sequence that isunique to the selected service provider.

In FIG. 14, at step S311, processing is performed in a case where theclient has selected the service A, whereas at steps S321-S323,processing is performed in a case where the client has selected theservice B. For example, the processing of the step S311 is executed forlog in to the service-offering server A, which offers the service A. Aunique API [GET login] that is supplied from the service provider A,which manages the service-offering server A, is applied to this loginprocessing. The interchange server has been set in advance in such amanner that it can use all APIs that are supplied from all serviceproviders. Having been preset as above, the interchange server selectsone API that should be applied on the basis of the service selectioninformation that is sent from the client and then uses the selected API.

If the client has selected the service B, the steps S321-S323 areexecuted for login to the service-offering server B. In order to log into the service-offering server B, which offers the service B, three APIsthat are unique to the service B are used. More specifically, [GETgetservicetoken], [GET servicelogin], and [GET getsession] are used forlog in to the service-offering server B. Processing for log in to theservice-offering server B is executed with the application of thesethree APIs.

If the client executed login directly to the service-offering server B,which offers the service B, it would be necessary for the client to usethese three APIs, unlike the configuration according to the presentembodiment of the invention. In this respect, however, since theinterchange server executes service login to the selected service inplace of the client in the configuration according to the presentembodiment of the invention, it is possible for the client to always usea common API (step S305) irrespective of which service is used.

FIG. 15 is an example of the application of APIs for image uploadprocessing. The client sets an image(s) to be uploaded in the uploadimage setting box 203 of the user interface (UI) (refer to FIGS. 8 and9) that is displayed on the display screen so as to be used forperforming image upload processing. In addition, the client enters datain each data input field of the user interface (UI) and, after theinputting of data, depresses the upload button. Through the uploadingmanipulation explained above, a common API [POST upload] is executed.This API is also a common API, which is common to all services.

The common API [POST upload] is an API that is used for transmittingupload image(s) and inputted data that are set in the upload imagesetting box 203 of the image-uploading user interface (UI) (refer toFIGS. 8 and 9) to the interchange server.

Upon the reception of the upload data from the client, as done in thelogin processing explained above, the interchange server uses an APIthat is provided by the service provider that corresponds to the servicespecified by the client so as to execute image upload processing. Thatis, the interchange server executes image upload processing thatcorresponds to a sequence that is unique to the selected serviceprovider.

In FIG. 15, at step S341, processing is performed in a case where theclient has selected the service A, whereas at step S351 processing isperformed in a case where the client has selected the service B. Forexample, the processing of the step S341 is executed for uploading animage(s) to the service-offering server A, which offers the service A. Aunique API [POST upload A] that is supplied from the service provider A,which manages the service-offering server A, is applied to this imageupload processing.

The processing of the step S351 is executed for uploading an image(s) tothe service-offering server B, which offers the service B. A unique API[POST upload B] that is supplied from the service provider B, whichmanages the service-offering server B, is applied to this image uploadprocessing.

As explained above, in the configuration according to the presentembodiment of the invention, the interchange server performs processingwhile using an API that corresponds to the service-offering server so asto perform processing in accordance with a sequence that is unique tothe service-offering server. In contrast, it is possible for the clientto perform processing while using a common API, which is common to allservice-offering servers, irrespective of which service is used.

In addition, in a case where a program/API is updated at theservice-offering server, the interchange server acquires the updatedprogram/API and uses thereof, which makes it unnecessary for the clientto perform any updating processing for the program/API. Thus, the burdenof the client is substantially reduced.

As has already been explained above, the client that performs processingwith the use of the common API of FIGS. 13-15 is not limited to theclient 101 of FIG. 1. That is, the Web server 105 also performsprocessing with the use of the common API.

With reference to FIG. 16, an example of the hardware configuration ofeach of a client, an interchange server, and a service-offering serveris explained below.

In FIG. 16, the client 510 is provided with a control unit 511 thatperforms data processing while using various programs/APIs, acommunication unit 512 that performs communication via a network, amemory unit 513 that memorizes programs, APIs, parameters, image data,and the like, a display unit 514 that displays, for example, an imageand a user interface, and an input unit 515 that inputs usermanipulation information. The display unit may function also as theinput unit if, for example, the client 510 has a configuration thataccepts an input via UI. An example of such a configuration is a touchpanel UI.

As has already been explained in the foregoing exemplary embodiment ofthe present advancement, the control unit 511 of the client 510selectively applies a plurality of APIs (Application ProgrammingInterface) that define execution processing and performs communicationwith a service-offering server through the intermediary of aninterchange server so as to use a service that is offered by theservice-offering server. When using any service among a plurality ofservices different from one another, which are offered by a plurality ofservice-offering servers, the control unit 511 performs processing withthe use of a common API.

When performing processing for the use of a service, for example, thecontrol unit 511 uses the common API so as to transmit service selectioninformation to the interchange server and receives service detailinformation corresponding to the selected service from the interchangeserver; the control unit 511 uses user interface generation informationthat is contained in the received service detail information so as todisplay a user interface; and the control unit 511 uses the common APIso as to transmit information that is inputted via the user interface tothe interchange server.

As has been explained earlier while referring to FIGS. 13-15, the commonAPI includes a login processing execution API, which defines loginfunctions that should be executed for using a service that is offered bythe service-offering server. When using the service-offering server, thecontrol unit 511 uses, after that login information defined in a userinterface generated on the basis of the service detail information hasbeen inputted, the login functions so as to transmit the logininformation to the interchange server. The interchange server uses thelogin information that is received from the client so as to execute alogin processing sequence that is unique to the service-offering serverthat corresponds to the service selected by the client.

In addition, the common API includes an image upload function that is tobe used for executing image upload processing, which is a service thatis offered by the service-offering server. When using theservice-offering server, the control unit 511 uses, after that data hasbeen inputted in an upload image setting portion defined in a userinterface generated on the basis of the service detail information, theimage upload function so as to transmit upload information to theinterchange server. The interchange server uses the upload informationthat is received from the client so as to execute an upload processingsequence that is unique to the service-offering server that correspondsto the service selected by the client.

As has already been explained above, the service detail informationincludes upload sequential order prescription information thatprescribes upload sequential order for uploading a plurality of imagesto the service-offering server. When a plurality of images is to beuploaded to the service-offering server, the control unit 511 performsimage upload processing in accordance with the upload sequential orderprescription information.

Other functions are also included in the common API. For example, analbums function is included to determine a listing of client albums on aservice-offering server to which the client is logged in. A new albumfunction may be used to create new client albums on the service-offeringserver. Further, an image function may be used to display at the clientimages stored on the service-offering server, and an assets function maybe used to determine client assets stored on the service-offeringserver. Client assets including, for example, photos, videos, audiofiles and other media. As will be appreciated by one skilled in the artother functions are also possible without departing from the scope ofthe present disclosure.

In FIG. 16, the interchange server 520 is provided with a control unit521 that performs data processing while using various programs/APIs, acommunication unit 522 that performs communication via a network, and amemory unit 523 that memorizes programs, APIs, parameters, image data,and the like.

The control unit 521 of the interchange server 520 provides servicedetail information corresponding to a service selected by a client tothe client on the basis of service selection information that has beenreceived from the client. Then, the control unit 521 of the interchangeserver 520 receives data that has been inputted via a user interfacegenerated on the basis of the service detail information from theclient, and then transfers the received data to the service-offeringserver that corresponds to the selected service.

Moreover, as has been explained earlier while referring to FIGS. 13-15,the control unit 521 uses a unique API, which is unique to theservice-offering server that offers the service selected by the client,so as to execute a login processing sequence that is unique to theservice-offering server or an upload processing sequence that is uniqueto the service-offering server upon the reception of login informationor upload data from the client.

Furthermore, the control unit 521 of the interchange server 520 receivesURLs from the service-offering server as information for accessing thedata uploaded from the client, and performs URL selection processing soas to select a URL that should be transmitted to the client on the basisof the upload data or the modes of service offered by theservice-offering server. This is the selection processing that hasalready been explained above while referring to the flowchart of FIG.12.

The service-offering server 530 is provided with a control unit 531 thatperforms data processing while using various programs/APIs, acommunication unit 532 that performs communication via a network, and amemory unit 533 that memorizes programs, APIs, parameters, image data,and the like.

Note that a Web server has, basically, the same configuration as that ofthe client 510 shown in FIG. 16 except that the Web server is notprovided with the display unit and the input unit of the client 510.Each of the clients 101 and 102 has fundamentally the same configurationas that of the client 510 shown in FIG. 16 except that the program/APIexecution function of the client 102 is inferior to that of the client101. Despite the fact that the program/API execution function of theclient 102 is inferior to that of the client 101, since the client B isprovided with a browsing function, the client 102 can perform imageupload processing and browsing processing just in the same manner asdone by the client 101 by displaying a web page that is presented by theWeb server.

A series of processing that is explained in this specification can beimplemented by means of hardware, software, or a combination of hardwareand software. If the series of processing that is explained in thisspecification is implemented by means of software, a set ofcomputer-readable instructions may be installed in a memory of acomputer that is built in dedicated hardware or installed in a generalpurpose computer that is capable of performing various kinds ofprocessing. For example, the computer-readable instructions may bepre-stored in a computer-readable recording medium. Thecomputer-readable instructions may be installed on a computer from arecording medium, or the computer-readable instructions may be receivedvia a network such as LAN (Local Area Network) or the Internet and theninstalled on a recording medium such as an internal/integral hard diskor the like.

Note that computer-readable instructions according to an aspect of theadvancement are, for example, a computer program that can be provided toa general purpose computer system that can execute various program codesin a computer-readable form of a storage medium or a communicationmedium. Since such a program is provided in the computer-readable form,processing is achieved in accordance with the program on the computersystem.

Further, various kinds of processing that are described in thisspecification are not necessarily executed in time series in accordancewith the order of appearance in this specification. That is, dependingon the processing capability of an apparatus/apparatuses that performsprocessing and/or according to need, processing may be performed in aparallel manner or on an individual basis. The term “system” used inthis specification means a logical set of a plurality of apparatuses. Itshould be noted that the apparatuses are not necessarily built in thesame single frame/housing.

As explained above, an image processing system according to an exemplaryembodiment of the invention includes a plurality of service-offeringservers, a client that uses services offered by the plurality ofservice-offering servers, and an interchange server that performsintermediary processing when the client uses a service. In such aconfiguration, the client performs communication with the interchangeserver while using a common API when using any service among a pluralityof services different from one another, which are offered by theplurality of service-offering servers. The interchange server uses aunique API, which is unique to the service-offering server that offersthe service selected by the client, so as to execute a processingsequence that is unique to the service-offering server. Such aconfiguration makes it possible for the client to use any service amongservices offered by the plurality of service-offering servers with theuse of a common API without any need to use a unique API, which isunique to each of the plurality of service-offering servers.

Obviously, numerous modifications and variations of the presentinvention are possible in light of the above teachings. It is thereforeto be understood that within the scope of the appended claims, theinvention may be practiced otherwise than as specifically describedherein.

1. A method of causing an interchange server to intermediatecommunication between a client device and a plurality ofservice-offering servers, the method comprising: generating a uniformuser interface at the client device in accordance with a common API, thecommon API being independent of a plurality of server-specific APIs eachcorresponding to a respective one of the plurality of service-offeringservers, the plurality of server-specific APIs being stored in anelectronic memory of the interchange server; receiving, at theinterchange server, input data entered into the uniform user interface,the input data including selection of a service corresponding to adesired service-offering server of the plurality of service offeringservers; translating the input data, at the interchange server, inaccordance with a respective one of the server-specific APIscorresponding to the desired service-offering server; and transmittingthe translated input data from the interchange server to the desiredservice-offering server in accordance with the respective one of theplurality of server-specific APIs, a response from the desiredservice-offering server being translated and transmitted to the clientdevice according to the common API.
 2. The method according to claim 1,further comprising: determining, at the interchange server, newservice-offering servers; and storing, in the electronic memory of theinterchange server, server-specific APIs corresponding to the newservice-offering servers.
 3. The method according to claim 1, furthercomprising: determining, at the interchange server, available serviceson the plurality of service-offering servers; transmitting a list of theavailable services to the client device in accordance with the commonAPI, the available services being incorporated into the uniform userinterface; and removing services corresponding to unavailableservice-offering servers from the user interface.
 4. The methodaccording to claim 1, further comprising: validating, at the interchangeserver, the input data using a machine-specific informationcorresponding to the client device, the machine-specific informationbeing previously stored in the interchange server.
 5. The methodaccording to claim 4, further comprising: generating a checksum at theclient device using the machine specific information; appending thechecksum to the input data at the client device; and verifying thechecksum at the interchange server using the machine-specificinformation.
 6. The method according to claim 1, wherein the common APIincludes a login function to log the client device onto the desiredservice-offering server, an albums function to return, via theinterchange server to the client device, a listing of data groups storedon the desired service-offering server, the data groups being associatedwith the client device at the desired service-offering server, a newalbum function to generate, via the interchange server, a new data groupin the desired service-offering server, an assets function to return,via the interchange server to the client device, a list of assets storedon the desired service-offering server, the list of assets beingassociated with the client device at the desired service-offeringserver, an image function to return selected data via the interchangeserver to the client device, the selected data being displayed on adisplay of the client device, and an upload function to upload the inputdata, via the interchange server, to the desired service-offeringserver.
 7. The method according to claim 6, wherein the common APIgenerates one of XML-formatted data and JSON-formatted data.
 8. Aninterchange server interposed between a client device and a plurality ofservice-offering servers, comprising: a client interface unit tocommunicate with the client device according to a common API, datareceived from the client device via the client interface unit includingselection of a service provided by a desired one of the service-offeringservers; a controller unit to translate the data received from theclient device in accordance with a respective one of a plurality ofserver-specific APIs stored in an electronic memory of the interchangeserver, each of the server-specific APIs corresponding to one of theplurality of service-offering servers; and a server interface unit tocommunicate, independently of the client interface unit, with thedesired service-offering server in accordance with the respective one ofthe plurality of server-specific APIs, a response received from thedesired service-offering server being translated and sent in accordancewith the common API to the client device via the client interface unit,wherein the common API provides a uniform interface to access servicesoffered by the plurality of service-offering servers via the pluralityof server-specific APIs.
 9. The interchange server according to claim 8,wherein the controller unit dynamically updates the plurality ofdifferent server-specific APIs in response to updates by the pluralityof service-offering servers.
 10. The interchange server according toclaim 8, wherein the controller unit dynamically stores newserver-specific APIs corresponding to newly detected service-offeringservers and dynamically removes server-specific APIs corresponding tounavailable service-offering servers.
 11. The interchange serveraccording to claim 8, further comprising: a validation unit to validatethe data received from the client device in accordance withmachine-specific information corresponding to the client device, themachine-specific information being previously stored in the interchangeserver.
 12. The interchange server according to claim 11, wherein thevalidation unit validates a checksum generated by the client device inaccordance with the machine-specific information.
 13. The interchangeserver according to claim 11, wherein the controller unit includes aservices unit to determine services provided by the plurality ofservice-offering servers, an album unit to determine groups of datastored on the desired service-offering server, a new album unit togenerate a new group of data in the desired service-offering server, animage unit to request selected data via the respective one of theplurality of server-specific APIs, the selected data being supplied tothe client device via the common API, the selected data being selectedat the client device, and an upload unit to supply data received fromthe client to the desired service-offering server via the respective oneof the plurality of server-specific APIs.
 14. The interchange serveraccording to claim 8, wherein the common API is used to generate atleast one of XML-formatted data and JSON-formatted data.
 15. Acomputer-readable medium storing computer-readable instructions thereon,the computer-readable instructions when executed by a computer cause thecomputer to perform the method comprising: generating a uniform userinterface at a client device in accordance with a common API, the commonAPI being independent of a plurality of server-specific APIs eachcorresponding to a respective one of a plurality of service-offeringservers, the plurality of server-specific APIs being stored in anelectronic memory of an interchange server; receiving, at theinterchange server, input data entered into the uniform user interface,the input data including selection of a service corresponding to adesired service-offering server of the plurality of service offeringservers; translating the input data in accordance with a respective oneof the server-specific APIs corresponding to the desiredservice-offering server; and transmitting the translated input data fromthe interchange server to the desired service-offering server inaccordance with the respective one of the plurality of server-specificAPIs, a response from the desired service-offering server beingtranslated and transmitted to the client device according to the commonAPI.
 16. The computer-readable medium according to 15, furthercomprising: determining new service-offering servers; and storing, inthe electronic memory of the interchange server, server-specific APIscorresponding to the new service-offering servers.
 17. Thecomputer-readable medium according to 15, further comprising:determining available services on the plurality of service-offeringservers; transmitting a list of the available services from theinterchange server to the client device in accordance with the commonAPI, the available services being incorporated into the uniform userinterface; and removing services corresponding to unavailableservice-offering servers from the uniform user interface.
 18. Thecomputer-readable medium according to claim 15, further comprising:validating the input data using machine-specific informationcorresponding to the client device, the machine specific-informationbeing previously stored in the interchange server.
 19. Thecomputer-readable medium according to claim 18, further comprising:generating a checksum at the client device using the machine-specificinformation; appending the checksum to the input data at the clientdevice; and verifying the checksum at the interchange server using themachine-specific information.
 20. The computer-readable medium accordingto claim 15, wherein the common API includes a login function to log theclient device onto the desired service-offering server, an albumsfunction to return, via the interchange server to the client device, alisting of data groups stored on the desired service-offering server,the data groups being associated with the client device at the desiredservice-offering server, a new album function to generate, via theinterchange server, a new data group in the desired service-offeringserver, an assets function to return, via the interchange server to theclient device, a list of assets stored on the desired service-offeringserver, the list of assets being associated with the client device atthe desired service-offering server, an image function to returnselected data via the interchange server to the client device, theselected data being displayed on a display of the client device, and anupload function to upload the input data, via the interchange server, tothe desired service-offering server.